-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[ntuple] rename 'leaf' structural role to 'plain' #19502
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
74816d1
to
b5897c4
Compare
Test Results 21 files 21 suites 3d 9h 33m 4s ⏱️ For more details on these failures, see this check. Results for commit 0b31cde. ♻️ This comment has been updated with latest results. |
b5897c4
to
133130d
Compare
133130d
to
174de14
Compare
174de14
to
37bd740
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
37bd740
to
d541b57
Compare
The name 'plain field' should better describe the actual structural role (resp. the absence of a structural role) of these fields. No change to the on-disk data.
d541b57
to
0b31cde
Compare
The structural role "leaf" was ill-named because in the tree of fields also inner nodes can carry that role. Hence renamed to "plain". Plain nodes are either leaves or they are inner "wrapper fields" with exactly one child field of the same cardinality (same number of elements modulo field repetition).
No changes to the on-disk format.